ci: publish to codemod#76
Merged
bjohansebas merged 1 commit intomainfrom Nov 7, 2025
Merged
Conversation
Signed-off-by: Sebastian Beltran <bjohansebas@gmail.com>
bjohansebas
force-pushed
the
codemod-publish
branch
from
25e06d2 to
1d65fd6
Compare
bjohansebas
changed the title
bjohansebas
force-pushed
the
codemod-publish
branch
from
1d65fd6 to
980f928
Compare
Member
Author
|
The force push was to remove the change I was making to the CI, but I think I’d rather make that change in a separate PR to adapt it to the new infrastructure that the package will use, which ideally will follow the one Node.js has. |
kjugi
approved these changes
Nov 2, 2025
Contributor
|
It's look good to me. But I assume that you (express) will use this ci to publish to the Codemod Registry |
Member
Author
yes! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Many thanks to the Node.js team for the CI setup they have for publishing to the codemod platform. I made some changes so that publishing now requires approval through a GitHub environment.
You just need to add
environment: publishand the environment has the following configuration to reduce the chance of new codemods being published without prior authorization from a team member.
I also created a token that exists only within the environment. It’s valid for one year, but I can change the token’s duration if that seems too long, though I don’t think we’ll want to be rotating it too frequently.